Differentiated services for protocol suitable network virtualization overlays

ABSTRACT

An approach is provided in which an information handling system receives, at a network virtualization edge (NVE), a set of Diffserv parameters comprising at least one classifier parameter, at least one meter parameter, at least one marker parameter, and at least one shaper/dropper parameter. The NVE performs a deep inspection on a plurality of data packets to classify the plurality of data packets at one or more classification levels. In turn, the NVE passes the set of Diffserv parameters and the one or more classification levels to underlay switch hardware.

BACKGROUND

Differentiated services (DiffServ) is a computer network protocol thatspecifies a scalable and coarse-grained mechanism for classifying andmanaging network traffic to provide quality of service (QoS) on modernInternet protocol (IP) networks. DiffServ operates on the principle oftraffic classification, whereby each data packet is classified into aparticular traffic class. Each traffic class may be managed differentlyfrom a QoS perspective to ensure preferential treatment forhigher-priority traffic on the network, such as providing low-latencycapability to critical network traffic, such as voice or streamingmedia, while providing simple best-effort service to non-criticalservices, such as web traffic or file transfers. DiffServ classifiespackets and policing at the “edges” of the network and uses a 6-bitdifferentiated services code point (DSCP) for packet classification inan 8-bit differentiated services field (DS field) in the IP header.

Computer networking has gravitated to cloud computing as a preferredcomputing environment due to its versatility over traditional computernetworks. One aspect of a cloud-computing environment's versatility isits ability to support multiple tenants. To support multiple tenants,cloud-computing environments may employ network virtualization, whichprovides each tenant its own address space that may overlap othertenants' address spaces. Network virtualization involves packetencapsulation, and Network virtualization over layer 3 (NVO3) isbecoming one of the preferred packet encapsulation approaches. NVO3provides a tunnel technology that encapsulates layer 2 packets to thelayer 3 layer and adds an overlay header to extend and divide neededaddress spaces.

BRIEF SUMMARY

According to one embodiment of the present disclosure, an approach isprovided in which an information handling system receives, at a networkvirtualization edge (NVE), a set of Diffserv parameters comprising atleast one classifier parameter, at least one meter parameter, at leastone marker parameter, and at least one shaper/dropper parameter. The NVEperforms a deep inspection on a plurality of data packets to classifythe plurality of data packets at one or more classification levels. Inturn, the NVE passes the set of Diffserv parameters and the one or moreclassification levels to underlay switch hardware.

The foregoing is a summary and thus contains, by necessity,simplifications, generalizations, and omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the present disclosure,as defined solely by the claims, will become apparent in thenon-limiting detailed description set forth below.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The present disclosure may be better understood, and its numerousobjects, features, and advantages made apparent to those skilled in theart by referencing the accompanying drawings, wherein:

FIG. 1 is a block diagram of a data processing system in which themethods described herein can be implemented;

FIG. 2 provides an extension of the information handling systemenvironment shown in FIG. 1 to illustrate that the methods describedherein can be performed on a wide variety of information handlingsystems which operate in a networked environment;

FIG. 3 is an exemplary diagram depicting a network virtualization edgeand an underlay Top of Rack (ToR) switch providing differentiatedservices (DiffServ) in a cloud environment utilizing a networkvirtualization over layer 3 (NVO3) protocol;

FIG. 4 is an exemplary flowchart depicting steps taken to configure anetwork virtualization edge and underlay ToR switch to provide DiffServcapabilities in a cloud environment that implements an NVO3 virtualoverlay protocol;

FIG. 5 is an exemplary diagram depicting various DiffServ configurationparameters that are sent by an network virtualization edge to anunderlay ToR switch;

FIG. 6 is an exemplary diagram depicting DiffServ entries generated andutilized by a network virtualization edge and an underlay ToR switch toprovide DiffServ capabilities in an NVO3 cloud-based environment;

FIG. 7 is an exemplary flowchart depicting steps taken by a networkvirtualization edge and an underlay ToR switch to apply DiffServparameters to NVO3 encapsulated packets; and

FIG. 8 is an exemplary diagram depicting an NVO3 encapsulated datapacket with DiffServ information.

DETAILED DESCRIPTION

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present disclosure has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the disclosure in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the disclosure. Theembodiment was chosen and described in order to best explain theprinciples of the disclosure and the practical application, and toenable others of ordinary skill in the art to understand the disclosurefor various embodiments with various modifications as are suited to theparticular use contemplated.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions. The following detailed description willgenerally follow the summary of the disclosure, as set forth above,further explaining and expanding the definitions of the various aspectsand embodiments of the disclosure as necessary.

FIG. 1 illustrates information handling system 100, which is asimplified example of a computer system capable of performing thecomputing operations described herein. Information handling system 100includes one or more processors 110 coupled to processor interface bus112. Processor interface bus 112 connects processors 110 to Northbridge115, which is also known as the Memory Controller Hub (MCH). Northbridge115 connects to system memory 120 and provides a means for processor(s)110 to access the system memory. Graphics controller 125 also connectsto Northbridge 115. In one embodiment, Peripheral Component Interconnect(PCI) Express bus 118 connects Northbridge 115 to graphics controller125. Graphics controller 125 connects to display device 130, such as acomputer monitor.

Northbridge 115 and Southbridge 135 connect to each other using bus 119.In one embodiment, the bus is a Direct Media Interface (DMI) bus thattransfers data at high speeds in each direction between Northbridge 115and Southbridge 135. In another embodiment, a PCI bus connects theNorthbridge and the Southbridge. Southbridge 135, also known as theInput/Output (I/O) Controller Hub (ICH) is a chip that generallyimplements capabilities that operate at slower speeds than thecapabilities provided by the Northbridge. Southbridge 135 typicallyprovides various busses used to connect various components. These bussesinclude, for example, PCI and PCI Express busses, an ISA bus, a SystemManagement Bus (SMBus or SMB), and/or a Low Pin Count (LPC) bus. The LPCbus often connects low-bandwidth devices, such as boot ROM 196 and“legacy” I/O devices (using a “super I/O” chip). The “legacy” I/Odevices (198) can include, for example, serial and parallel ports,keyboard, mouse, and/or a floppy disk controller. Other components oftenincluded in Southbridge 135 include a Direct Memory Access (DMA)controller, a Programmable Interrupt Controller (PIC), and a storagedevice controller, which connects Southbridge 135 to nonvolatile storagedevice 185, such as a hard disk drive, using bus 184.

ExpressCard 155 is a slot that connects hot-pluggable devices to theinformation handling system. ExpressCard 155 supports both PCI Expressand Universal Serial Bus (USB) connectivity as it connects toSouthbridge 135 using both the USB and the PCI Express bus. Southbridge135 includes USB Controller 140 that provides USB connectivity todevices that connect to the USB. These devices include webcam (camera)150, infrared (IR) receiver 148, keyboard and trackpad 144, andBluetooth device 146, which provides for wireless personal area networks(PANs). USB Controller 140 also provides USB connectivity to othermiscellaneous USB connected devices 142, such as a mouse, removablenonvolatile storage device 145, modems, network cards, IntegratedServices Digital Network (ISDN) connectors, fax, printers, USB hubs, andmany other types of USB connected devices. While removable nonvolatilestorage device 145 is shown as a USB-connected device, removablenonvolatile storage device 145 could be connected using a differentinterface, such as a Firewire interface, etcetera.

Wireless Local Area Network (LAN) device 175 connects to Southbridge 135via the PCI or PCI Express bus 172. LAN device 175 typically implementsone of the Institute of Electrical and Electronic Engineers (IEEE)802.11 standards of over-the-air modulation techniques that all use thesame protocol to wireless communicate between information handlingsystem 100 and another computer system or device. Optical storage device190 connects to Southbridge 135 using Serial Analog Telephone Adapter(ATA) (SATA) bus 188. Serial ATA adapters and devices communicate over ahigh-speed serial link. The Serial ATA bus also connects Southbridge 135to other forms of storage devices, such as hard disk drives. Audiocircuitry 160, such as a sound card, connects to Southbridge 135 via bus158. Audio circuitry 160 also provides functionality such as audioline-in and optical digital audio in port 162, optical digital outputand headphone jack 164, internal speakers 166, and internal microphone168. Ethernet controller 170 connects to Southbridge 135 using a bus,such as the PCI or PCI Express bus. Ethernet controller 170 connectsinformation handling system 100 to a computer network, such as a LocalArea Network (LAN), the Internet, and other public and private computernetworks.

While FIG. 1 shows one information handling system, an informationhandling system may take many forms. For example, an informationhandling system may take the form of a desktop, server, portable,laptop, notebook, or other form factor computer or data processingsystem. In addition, an information handling system may take other formfactors such as a personal digital assistant (PDA), a gaming device,Automated Teller Machine (ATM), a portable telephone device, acommunication device or other devices that include a processor andmemory.

FIG. 2 provides an extension of the information handling systemenvironment shown in FIG. 1 to illustrate that the methods describedherein can be performed on a wide variety of information handlingsystems that operate in a networked environment. Types of informationhandling systems range from small handheld devices, such as handheldcomputer/mobile telephone 210 to large mainframe systems, such asmainframe computer 270. Examples of handheld computer 210 includepersonal digital assistants (PDAs), personal entertainment devices, suchas Moving Picture Experts Group Layer-3 Audio (MP3) players, portabletelevisions, and compact disc players. Other examples of informationhandling systems include pen, or tablet, computer 220, laptop, ornotebook, computer 230, workstation 240, personal computer system 250,and server 260. Other types of information handling systems that are notindividually shown in FIG. 2 are represented by information handlingsystem 280. As shown, the various information handling systems can benetworked together using computer network 200. Types of computer networkthat can be used to interconnect the various information handlingsystems include Local Area Networks (LANs), Wireless Local Area Networks(WLANs), the Internet, the Public Switched Telephone Network (PSTN),other wireless networks, and any other network topology that can be usedto interconnect the information handling systems. Many of theinformation handling systems include nonvolatile data stores, such ashard drives and/or nonvolatile memory. Some of the information handlingsystems shown in FIG. 2 depicts separate nonvolatile data stores (server260 utilizes nonvolatile data store 265, mainframe computer 270 utilizesnonvolatile data store 275, and information handling system 280 utilizesnonvolatile data store 285). The nonvolatile data store can be acomponent that is external to the various information handling systemsor can be internal to one of the information handling systems. Inaddition, removable nonvolatile storage device 145 can be shared amongtwo or more information handling systems using various techniques, suchas connecting the removable nonvolatile storage device 145 to a USB portor other connector of the information handling systems.

FIGS. 3 through 8 depict an approach that can be executed on aninformation handling system to provide differentiated services(DiffServ) features in a cloud computing environment that utilizes NVO3virtualization. Cloud computing environments that utilize NVO3virtualization require an approach to provide QoS capabilities. However,issues arise with the prior art because the DiffServ protocol embeds theDiffServ codepoints (DSCPs) into the IP header of a data packet and theNVO3 protocol encapsulates the data packet. As a result, the datapackets reaching an underlay ToR switch are encapsulated by the networkvirtualization edge and, therefore, undetectable by the underlay ToRswitch.

To solve the aforementioned issues with the prior art, the approachdescribed herein proceeds through a configuration stage and then apacket processing stage to enable a network virtualization edge toclassify egress data packets and an underlay ToR switch to applyDiffServ parameters based on the classification. During theconfiguration stage, a network virtualization edge receives DiffServcontrol information from a controller that includes classificationinformation and corresponding DiffServ parameters to apply to thepackets. The network virtualization edge stores the DiffServ controlinformation along with unique classification identifiers into aclassification entry area. Next, the network virtualization edge sendsDiffServ configuration information to the underlay ToR switch thatincludes the unique classification identifiers and correspondingDiffServ parameters. The underlay ToR switch stores the DiffServconfiguration information in a DiffServ parameters entry area tocomplete the configuration stage.

Next, the network virtualization edge receives an egress data packetfrom a virtual machine and classifies the data packet by matching thepacket's properties to one of the classification entries (e.g., tenantID, source IP addresses, etc.). The network virtualization edgedetermines the corresponding unique classification identifier andincludes the unique classification identifier in a networkvirtualization overlay header during encapsulation and sends theencapsulated data packet to the underlay ToR switch. The underlay ToRswitch extracts the unique classification identifier from the networkvirtualization overlay header and matches the unique classificationidentifier with one of the DiffServ parameter entries. In turn, theunderlay ToR switch applies the DiffServ parameters included in thematched entry to the encapsulated data packet and sends the encapsulateddata packet onto the computer network.

FIG. 3 is an exemplary diagram depicting a network virtualization edge(NVE) and an underlay Top of Rack (ToR) switch providing differentiatedservices (DiffServ) in a cloud environment that utilizes a networkvirtualization over layer 3 (NVO3) protocol.

Prior to being able to apply DiffServ features to egress data packets,controller 300, network virtualization edge 310, and underlay ToR switch330 proceed through a configuration stage. During the configurationstage, an administrator uses controller 300 to provide DiffServ controlinformation 305 to each of network virtualization edge 310's thatoperate in a cloud environment. DiffServ control information 305includes various DiffServ classification rules and DiffServ parametersto apply to each of the various DiffServ classification rules. In oneembodiment, DiffServ control information 305 includes DiffServclassification rules and corresponding DiffServ parameters for multipletenants operating in the cloud environment. In this embodiment, theDiffServ classification rules may be based on packet parameters such astenant, source port of a virtual machine, data source IP of a virtualmachine, and/or various ACL (access control list) rules.

Network virtualization edge 310 receives DiffServ control information305 and generates DiffServ classification entries 315, which include aunique identifier and classification rules for each entry (see FIG. 6and corresponding text for further details). In one embodiment, networkvirtualization edge 315 may generate a balanced classificationidentifier based on the unique classification identifier andcorresponding packet properties to achieve a desired virtual machine tovirtual machine equal-cost multi-path (ECMP)/load balancing (see FIG. 4and corresponding text for further details).

Next, network virtualization edge 310 sends DiffServ configurationinformation 320 to underlay ToR switch 330. Network virtualization edge310 provides DiffServ configuration information 320 because egress datapackets that will be sent by network virtualization edge 310 to underlayToR switch 330 are encapsulated via NVO3 and, therefore, DiffServparameters traditionally stored in the “inner” egress data packet'sheader are unreadable by underlay ToR switch 330. To solve this issue,network virtualization edge 310 sends DiffServ configuration information320 to underlay ToR switch 330 that includes DiffServ information thatmaps the DiffServ classification identifiers embedded in the networkvirtualization overlay header to the DiffServ parameters. Underlay ToRswitch 330 stores the information in DiffServ parameters entries 335 tocomplete the configuration stage (see FIG. 6 and corresponding text forfurther details).

Now that the DiffServ configuration stage is complete, networkvirtualization edge 310 is able to receive egress packet 345 fromvirtual machine (VM) 340 and analyze packet 345 against the DiffServclassification rules in DiffServ classification entries 315. Forexample, packet 345 may include packet properties corresponding totenant XYZ and classification entries 315 includes a classification rulefor tenant XYZ's egress data packets.

When network virtualization edge 310 matches a DiffServ classificationentry, network virtualization edge 315 identifies the DiffServclassification entry's corresponding DiffServ classification identifierin classification entries 315 and inserts the DiffServ classificationidentifier into packet 345's network virtualization overlay header (alsoreferred to herein as overlay header) during NVO3 encapsulation (seeencapsulated packet 350). In one embodiment, network virtualization edge310 inserts the DiffServ classification identifier in the source portfield of the overlay UDP (user datagram protocol) field because the16-bit source port of the overlay UDP field may be changed withoutaffecting the packet forwarding (see FIG. 8 and corresponding text forfurther details).

Underlay ToR switch 330 receives encapsulated packet 350 and extractsthe DiffServ classification identifier from the overlay header. UnderlayToR switch 330 then matches the classification identifier with entriesin DiffServ parameter entries 335 to determine which DiffServ parametersto apply to encapsulated packet 350. Underlay ToR switch 330 applies theDiffServ parameters and, in one embodiment, inserts correspondingdifferentiated services codepoint (DSCP) bits into the type of servicefield in the overlay header (see encapsulated packet 360) for downstreamDiffServ processing purposes. In turn, underlay ToR switch 330 sendsencapsulated packet 360 onto underlay aggregation switch 370, whichsends encapsulated packet 360 to a destination virtual machine viacomputer network 380.

FIG. 4 is an exemplary flowchart depicting steps taken to configure anetwork virtualization edge and an underlay ToR switch to provideDiffServ capabilities in a cloud environment with an NVO3 virtualoverlay implementation. Network virtualization edge configurationprocessing commences at 400 whereupon, at step 410, the networkvirtualization edge receives DiffServ control information fromcontroller 300. The DiffServ control information may include DiffServclassification rules, DiffServ classification identifiers, and DiffServparameters.

At step 420, the network virtualization edge generates DiffServclassification entries 315 from the DiffServ control information. In oneembodiment, DiffServ classification entries 315 include an entry foreach DiffServ classification rule along with its corresponding DiffServparameters and DiffServ classification identifier. The networkvirtualization edge, at step 425, inserts the DiffServ classificationidentifiers into each entry, which the network virtualization edgesubsequently utilizes to convey a packet's DiffServ classification tothe underlay ToR switch (see FIG. 6 and corresponding text for furtherdetails). In one embodiment. the network virtualization edge generatesbalanced classification identifiers, such as when the networkvirtualization edge would not be able to achieve a desired VM-VMequal-cost multi-path (ECMP)/load balancing. For example, in thisembodiment, the network virtualization edge generates balancedclassification identifiers for rules that may 1) only match tenant ID;2) only match the source port of virtual machine; or 3) only match thesource IP of virtual machine. The network virtualization edge may use analgorithm such as:Balanced Class ID=Base Class ID+(Hash(Inner Packet)) % Nwhere N is the number of ECMP/Load balancers according to the size ofECMP supported on a current underlay ToR switch.

At step 430, the process transmits DiffServ configuration information320 to the underlay ToR switch. In one embodiment, DiffServconfiguration information 320 includes DiffServ classificationidentifiers (or balanced classification identifiers) and theircorresponding DiffServ parameters (see FIG. 5 and corresponding text forfurther details). Network virtualization edge processing thereafter endsat 440.

Underlay ToR switch configuration processing commences at 450 whereupon,at step 460, the underlay ToR switch receives DiffServ configurationinformation 320 from the network virtualization edge. At step 470, theunderlay ToR switch parses DiffServ configuration information 320 andidentifies the DiffServ classification identifiers and correspondingDiffServ parameters. The underlay ToR switch, at step 480, stores theDiffServ classification identifiers with their corresponding DiffServparameters in DiffServ parameter entries 335 (see FIG. 6 andcorresponding text for further details). Underlay ToR switch processingthereafter ends at 495.

FIG. 5 is an exemplary diagram depicting DiffServ configurationinformation 320 sent by the network virtualization edge to the underlayToR switch. The example shown in FIG. 5 depicts DiffServ configurationinformation 320 in a link layer discovery protocol (LLDP) format thatadopts a type-length value (TLV) structure. As those skilled in the artcan appreciate, network virtualization edge 310 may use differentprotocols and/or formats to provide DiffServ configuration informationto underlay ToR switch 330.

The example shown in FIG. 5 includes five TLV structures in DiffServconfiguration information 320. As those skilled in the art canappreciate, more or less TLV structures may be included in DiffServconfiguration information 320. TLV1 500 indicates a classificationidentifier corresponding to a DiffServ classification entry inclassification entries 315. TLV2 510 identifies a Classifier Type with avalue of 0 to indicate that the DiffServ classification identifier willbe located in the overlay header's UDP source port field. In oneembodiment, the classifier type may be changed to a different value toindicate that DiffServ classification identifier will be in a differentheader field.

TLV3 520 includes a UDP source port value such as “FID2,” which is theDiffServ classification identifier that corresponds to the DiffServparameters in TLV 4 530 and TLV 5 540. Underlay ToR switch 330, in turn,generates DiffServ parameter entries 335 using the information fromDiffServ configuration information 320 (see FIG. 6 and correspondingtext for further details).

FIG. 6 is an exemplary diagram depicting DiffServ entries generated andutilized by a network virtualization edge and an underlay ToR switch toprovide DiffServ capabilities in a NVO3 cloud-based environment. In oneembodiment, DiffServ classification entries 315 includes DiffServclassification entries based on factors such as an egress packet'scorresponding tenant, the source port of a virtual machine, the datasource IP address of a virtual machine, and/or various ACL rules. Inanother embodiment, the entries in DiffServ classification entries 315are organized in order of importance and the network virtualization edgeapplies the most important DiffServ parameters to a packet. For example,network virtualization edge 310 may compare packet properties to thefirst DiffServ entry and, if a match does not occur, networkvirtualization edge 310 compares the packet properties to the secondentry, and so on.

DiffServ parameter entries 335 includes entries generated by underlayToR switch 330 based on DiffServ configuration information 320. Eachentry includes a DiffServ classification identifier and correspondingDiffServ parameters to apply to encapsulated egress data packets. Asdiscussed herein, underlay ToR switch 330 matches DiffServclassification identifiers extracted from overlay headers ofencapsulated packets with entries in DiffServ parameter entries 335 andapplies the corresponding DiffServ parameters to the encapsulatedpackets.

FIG. 7 is an exemplary flowchart depicting steps taken by a networkvirtualization edge and an underlay ToR switch to apply DiffServparameters to NVO3 encapsulated data packets. Network virtualizationedge processing commences at 700 whereupon, at step 710, the networkvirtualization edge receives a data packet (packet 345) from VM 340 andmatches the data packet's properties to a DiffServ classification rulein DiffServ classification entries 315. For example, a DiffServclassification rule may be based on a tenant ID that matches the tenantID of packet 345. In another example, a classification rule may be basedon the source port of VM 340 that provided packet 345 and the networkvirtualization edge matches VM 340 to the particular classificationrule.

At step 720, the network virtualization edge identifies a DiffServclassification identifier in the DiffServ classification rule thatcontains the matched DiffServ classification rule and, at step 725, thenetwork virtualization edge inserts the DiffServ classificationidentifier into the network virtualization overlay header's UDP sourceport during NVO3 encapsulation. Referring to FIG. 8, networkvirtualization edge 310 inserts classification ID 800 into the sourceport field of the outer UDP header during encapsulation. At step 730,the network virtualization edge sends encapsulated data packet 350 tothe underlay ToR switch and network virtualization edge processingthereafter ends at 740.

Underlay ToR switch processing commences at 750 whereupon, at step 760,the underlay ToR switch receives encapsulated data packet 350. At step770, the underlay ToR switch extracts the DiffServ classificationidentifier from the UDP source port field and matches the DiffServclassification identifier to an entry in DiffServ parameter entries 335.For example and referring to FIG. 6, encapsulated data packet 350'sDiffServ classification identifier may be “FID1” and the underlay ToRswitch matches the DiffServ classification identifier to the entry inDiffServ parameter entries 335.

At step 780, in one embodiment and referring to FIG. 8, the underlay ToRswitch inserts/modifies differentiated services code point (DSCP) 810 inthe outer IP field based on the identified DiffServ parameters fordownstream component processing. At step 790, the underlay ToR switchsends the encapsulated packet to underlay aggregation switch 370 basedon the DiffServ parameters and underlay ToR switch processing thereafterends at 795.

FIG. 8 is an exemplary diagram depicting an NVO3 encapsulated datapacket that includes a DiffServ classification identifier in its networkvirtualization overlay header. Network virtualization edge 310 receivespacket 345 and encapsulates packet 345 according to NVO3 protocols.During the encapsulation process, network virtualization edge 310inserts classification identifier 800 into the outer UDP source portfield as described herein. In one embodiment, network virtualizationedge 310 chooses the outer UDP source port field because, per industrystandards, the outer UDP source port field's value may be changedwithout affecting the packet forwarding process. As those skilled in theart can appreciate, network virtualization edge 310 may place theDiffServ classification identifier in other fields according to variousindustry standards or even a mixture of multiple fields.

When underlay ToR switch 330 receives encapsulated packet 350, underlayToR switch 330 identifies the DiffServ parameters to apply to the packetas discussed herein, and then may add DSCP 810 to the Type of Service(ToS) field in the outer IP header to inform downstream components howto process the packet.

While particular embodiments of the present disclosure have been shownand described, it will be obvious to those skilled in the art that,based upon the teachings herein, that changes and modifications may bemade without departing from this disclosure and its broader aspects.Therefore, the appended claims are to encompass within their scope allsuch changes and modifications as are within the true spirit and scopeof this disclosure. Furthermore, it is to be understood that thedisclosure is solely defined by the appended claims. It will beunderstood by those with skill in the art that if a specific number ofan introduced claim element is intended, such intent will be explicitlyrecited in the claim, and in the absence of such recitation no suchlimitation is present. For non-limiting example, as an aid tounderstanding, the following appended claims contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimelements. However, the use of such phrases should not be construed toimply that the introduction of a claim element by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim element to disclosures containing only one suchelement, even when the same claim includes the introductory phrases “oneor more” or “at least one” and indefinite articles such as “a” or “an”;the same holds true for the use in the claims of definite articles.

The invention claimed is:
 1. A method implemented by an informationhandling system that includes a memory and a processor, the methodcomprising: receiving, at a network virtualization edge (NVE), a set ofDiffserv parameters comprising at least one classifier parameter, atleast one meter parameter, at least one marker parameter, and at leastone shaper/dropper parameter; generating a set of classification levelsthat correspond to the set of Diffserv parameters; sending, by the NVE,a set of configuration information comprising the set of Diffservparameters and the corresponding set of classification levels to anunderlay switch hardware; encapsulating at least one data packet by theNVE, wherein the encapsulated at least one data packet comprises aclassification identifier corresponding to one of the set ofclassification levels; transmitting the encapsulated at least one datapacket from the NVE to the underlay switch hardware; matching, by theunderlay switch hardware, the classification identifier to one of theset of classification levels included in the received set ofconfiguration information; and processing, by the underlay switchhardware, the encapsulated data packet based on one or more of the setof Diffserv parameters, included in the received set of configurationinformation, that corresponds to the matched classification level. 2.The method of claim 1 further comprising: modifying, by the underlayswitch hardware, one or more overlay headers corresponding to theencapsulated at least one data packet according to the at least oneclassifier parameter.
 3. The method of claim 1 further comprising:modifying, by the underlay switch hardware, one or more overlay headerscorresponding to the encapsulated at least one data packet according tothe at least one meter parameter.
 4. The method of claim 1 furthercomprising: modifying, by the underlay switch hardware, one or moreoverlay headers corresponding to the encapsulated at least one datapacket according to the at least one marker parameter.
 5. The method ofclaim 1 further comprising: modifying, by the underlay switch hardware,one or more overlay headers corresponding to the encapsulated at leastone data packet according to the at least one shaper/dropper parameter.6. The method of claim 1 further comprising: negotiating, between theNVE and the underlay switch hardware, a QoS (quality of service)configuration.
 7. The method of claim 1 wherein the underlay switchhardware is an underlay Top of Rack (ToR) switch.
 8. An informationhandling system comprising: one or more processors; a memory coupled toat least one of the processors; and a set of computer programinstructions stored in the memory and executed by at least one of theprocessors in order to perform actions of: receiving, at a networkvirtualization edge (NVE), a set of Diffserv parameters comprising atleast one classifier parameter, at least one meter parameter, at leastone marker parameter, and at least one shaper/dropper parameter;generating a set of classification levels that correspond to the set ofDiffserv parameters; sending, by the NVE, a set of configurationinformation comprising the set of Diffserv parameters and thecorresponding set of classification levels to an underlay switchhardware; encapsulating at least one data packet by the NVE, wherein theencapsulated at least one data packet comprises a classificationidentifier corresponding to one of the set of classification levels;transmitting the encapsulated at least one data packet from the NVE tothe underlay switch hardware; matching, by the underlay switch hardware,the classification identifier to one of the set of classification levelsincluded in the received set of configuration information; andprocessing, by the underlay switch hardware, the encapsulated datapacket based on one or more of the set of Diffserv parameters, includedin the received set of configuration information, that corresponds tothe matched classification level.
 9. The information handling system ofclaim 8 wherein at least one of the one or more processors performadditional actions comprising: modifying, by the underlay switchhardware, one or more overlay headers corresponding to the encapsulatedat least one data packet according to the at least one classifierparameter.
 10. The information handling system of claim 8 wherein atleast one of the one or more processors perform additional actionscomprising: modifying, by the underlay switch hardware, one or moreoverlay headers corresponding to the encapsulated at least one datapacket according to the at least one meter parameter.
 11. Theinformation handling system of claim 8 wherein at least one of the oneor more processors perform additional actions comprising: modifying, bythe underlay switch hardware, one or more overlay headers correspondingto the encapsulated at least one data packet according to the at leastone marker parameter.
 12. The information handling system of claim 8wherein at least one of the one or more processors perform additionalactions comprising: modifying, by the underlay switch hardware, one ormore overlay headers corresponding to the encapsulated at least one datapacket according to the at least one shaper/dropper parameter.
 13. Theinformation handling system of claim 8 wherein at least one of the oneor more processors perform additional actions comprising: negotiating,between the NVE and the underlay switch hardware, a QoS (quality ofservice) configuration.
 14. The information handling system of claim 8wherein the underlay switch hardware is an underlay Top of Rack (ToR)switch.
 15. A computer program product stored in a computer readablestorage medium, comprising computer program code that, when executed byan information handling system, causes the information handling systemto perform actions comprising: receiving, at a network virtualizationedge (NVE), a set of Diffserv parameters comprising at least oneclassifier parameter, at least one meter parameter, at least one markerparameter, and at least one shaper/dropper parameter; generating a setof classification levels that correspond to the set of Diffservparameters; sending, by the NVE, a set of configuration informationcomprising the set of Diffserv parameters and the corresponding set ofclassification levels to an underlay switch hardware; encapsulating atleast one data packet by the NVE, wherein the encapsulated at least onedata packet comprises a classification identifier corresponding to oneof the set of classification levels; transmitting the encapsulated atleast one data packet from the NVE to the underlay switch hardware;matching, by the underlay switch hardware, the classification identifierto one of the set of classification levels included in the received setof configuration information; and processing, by the underlay switchhardware, the encapsulated data packet based on one or more of the setof Diffserv parameters, included in the received set of configurationinformation, that corresponds to the matched classification level. 16.The computer program product of claim 15 wherein the informationhandling system performs further actions comprising: modifying, by theunderlay switch hardware, one or more overlay headers corresponding tothe encapsulated at least one data packet according to the at least oneclassifier parameter.
 17. The computer program product of claim 15wherein the information handling system performs further actionscomprising: modifying, by the underlay switch hardware, one or moreoverlay headers corresponding to the encapsulated at least one datapacket according to the at least one meter parameter.
 18. The computerprogram product of claim 15 wherein the information handling systemperforms further actions comprising: modifying, by the underlay switchhardware, one or more overlay headers corresponding to the encapsulatedat least one data packet according to the at least one marker parameter.19. The computer program product of claim 15 wherein the informationhandling system performs further actions comprising: modifying, by theunderlay switch hardware, one or more overlay headers corresponding tothe encapsulated at least one data packet according to the at least oneshaper/dropper parameter.
 20. The computer program product of claim 15wherein the information handling system performs further actionscomprising: negotiating, between the NVE and the underlay switchhardware, a QoS (quality of service) configuration.